TrustRadius Insights
Docker has proven to be a versatile tool with a wide range of use cases. Users have found that Docker simplifies the packaging and …
Starting at $500 per year per node
View PricingOverview
What is Mirantis Kubernetes Engine?
The Mirantis Kubernetes Engine (formerly Docker Enterprise, acquired by Mirantis in November 2019)aims to let users ship code faster. Mirantis Kubernetes Engine gives users one set of APIs and tools to deploy, manage, and observe secure-by-default, certified, batteries-included Kubernetes clusters…
Recent Reviews
Pricing
Free
$0.00
Cloud
per year
Basic
$500.00
Cloud
per year
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://store.mirantis.com
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Starting price (does not include set up fee)
- $500 per year per node
Product Details
- About
- Tech Details
- FAQs
What is Mirantis Kubernetes Engine?
Mirantis Kubernetes Engine Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
Frequently Asked Questions
The Mirantis Kubernetes Engine (formerly Docker Enterprise, acquired by Mirantis in November 2019)aims to let users ship code faster. Mirantis Kubernetes Engine gives users one set of APIs and tools to deploy, manage, and observe secure-by-default, certified, batteries-included Kubernetes clusters on any infrastructure: public cloud, private cloud, or bare metal.
Mirantis Kubernetes Engine starts at $500.
Reviewers rate Support Rating highest, with a score of 7.8.
The most common users of Mirantis Kubernetes Engine are from Mid-sized Companies (51-1,000 employees).
Comparisons
Compare with
Reviews and Ratings
(210)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Recommendations
Docker has proven to be a versatile tool with a wide range of use cases. Users have found that Docker simplifies the packaging and deployment of applications and services, allowing developers to match their development environment to production and eliminate cross-cutting software dependencies. It has been utilized as the backbone of a hosted app infrastructure, where every element is broken down into microservices deployed on the AWS cloud. Additionally, Docker has been instrumental in creating specialized microservices such as a Selenium Grid for automated web-based testing.
Moreover, Docker has played a crucial role in maintaining environmental consistency and streamlining deployment processes. It has enabled users to swiftly containerize Continuous Deployment and Integration pipelines, facilitating easy deployment and updates of the system and its environments. With Docker, users have been able to quickly deploy and monitor servers, firewalls, switches, and other components, providing a consistent and efficient environment for prototyping and testing. Another notable use case is spinning up new databases for microservices using Docker, ensuring consistency and independence across different environments.
Furthermore, Docker has integrated seamlessly with orchestration frameworks like Apache Mesos and Mesosphere Marathon. This combination has allowed for more efficient application development and deployment through effective management of containers. Docker has also demonstrated its utility in building server deployment files and running tests, enabling consistent deployments and reliable testing procedures.
In addition to these technical applications, Docker has proved to be valuable in hosting MySQL databases for production websites. Its stability, security features, and easy provisioning of identical instances have made it a preferred choice for users. Moreover, Docker has been extensively used in CI builds as it enables the creation of custom Linux images and seamless deployment of the latest code from the Docker registry.
The flexibility offered by Docker comes to the forefront when it comes to testing practices. It provides a highly configurable environment that makes cross-platform testing significantly more efficient. Users have leveraged Docker for both automated website/application testing pipelines as well as creating flexible environments for manual testing. Moreover, Docker has acted as a viable alternative to custom build and deploy solutions, offering a more flexible and decentralized process.
Notably, Docker has been embraced by a large global financial services provider to enhance efficiency and agility in application development. This adoption has resulted in increased innovation and productivity within the organization. Another significant benefit of using Docker is its ability to provide identical application environments across multiple deployment environments, leading to the deployment of more stable applications.
Furthermore, Docker has played a role in differentiating between server/compute infrastructure and application infrastructure. Operations teams can efficiently manage the cluster of servers, while application developers can run containers on the cluster, ensuring a clear separation and easier management of the two layers.
Teams have leveraged Docker for various development and deployment practices. Engineers can build applications in the same environment, eliminating local configuration issues that often arise when working across different setups. Docker has been particularly useful for WordPress development, replacing tools like Vagrant and providing tighter integration with Windows Hyper-V and better performance.
One of the significant advantages of Docker is its ability to containerize applications, resulting in consistent deployment environments across different stages and compatibility with various cloud platforms. This has greatly simplified the deployment process for users and enhanced their productivity. Additionally, Docker has been highly beneficial for the development team in resolving issues related to different setups on Windows, Linux, and Mac operating systems, while also providing easy configurations for automation QA.
Docker's impact extends beyond software development into the realm of research reproducibility. Users have developed Docker containers to encapsulate research pipelines, leveraging GitHub and DockerHub as public repositories. This approach has effectively addressed the challenge of ensuring reproducibility in research experiments.
Moreover, Docker Swarm has been employed to deploy internal applications in a managed cluster, successfully tackling scaling and load balancing issues during peak business hours. The combination of Docker with Kubernetes has also gained popularity among teams for containerizing projects and facilitating the development of microservices.
Overall, Docker's value proposition lies in its ability to provide consistent development environments, prevent deployment issues, streamline configurations, enhance testing efficiency, and simplify the overall software packaging and deployment processes. Its widespread usage across various industries highlights its robustness, ease of setup, community support through open-sourced images, and its ability to create and test configurations as needed. Docker has become an indispensable tool for many organizations seeking to optimize their software development lifecycle while improving productivity and innovation.
Based on the reviews, here are the three most common recommendations:
-
Users recommend trying Docker for deploying web services and running micro-services. They suggest doing tutorials to learn how to create Dockerfiles and docker-compose files correctly. Additionally, they advise considering whether Docker is necessary or if statically linked binaries can be used instead.
-
Users also recommend using Docker for QA environments and setting up developers with the environment they need. They find Docker to be an easy-to-use development tool with great rewards for a small amount of effort. However, some users caution that while Docker is a good solution, there may be better alternatives available.
-
Another common recommendation is to carefully consider the use of Docker in a workflow and discuss its usability within the organization before implementing it. Users emphasize the importance of learning the basics of Docker and understanding if continuous integration/deployment is the right approach. They also mention that Docker has a supportive community and is widely used in the industry.
Overall, users suggest experimenting with Docker, especially for new applications or running micro-services. They recommend taking advantage of Docker's simplicity and portability while being mindful of specific requirements and considering other options if needed.
Attribute Ratings
Reviews
(1-22 of 22)Companies can't remove reviews or game the system. Here's why
Through
[Mirantis Cloud Native Suite (Docker Enterprise)] I have got rid of the improperly-signed and even unsigned container
workloads. This tool is easy to configure and easily I can tag the workloads
for execution on appropriate node types. Further through this application, it is
very convenient for me to use specialized hardware in bare metal which includes
FPGAs and GPUs, that offer great machine learning and helps in scientific
computing.
- It is advanced tool for balancing loads and managing routes.
- It is easy to edit container contents.
- Alerts are very useful which helps us handling the entire network.
- I am mostly satisfied with all of its features but I have faced issues in the continuous data storage no doubt they offer features like Dockers Data Volumes but still there is much room for improvement.
- Moreover, I am a happy user of this platform.
December 20, 2019
Docker Swarm: Simplify Multiple Deployments
We use Swarm to deploy internal applications in a managed cluster. These applications are mission-critical and used across all departments in the organization. Swarm solves the problem of scaling and load balancing traffic and resources during peak business hours. It allows fast and simple automated deployment which drastically reduces the time spent on this task by developers.
- Managing a cluster of micro-services.
- Redundancy, fault-tolerance, and load balancing.
- Small community - not a lot of information available outside of the documentation.
- Logging - centralized logging for all applications is something we wish was available.
July 20, 2019
Docker: The Little "VM" That Could!
We are currently using Docker in a test environment to deploy and monitor all of our servers/firewalls/switches/etc. throughout our company. We have a single server instance that houses all the containers and images. My department, the technology services department, is the only department that uses this and as it is still only being tested only one user is using/deploying/managing it—me. But it allows me to have a glance at each location to see if there are any issues that could potentially take down a site.
- Usability is great after the initial setup.
- Installation is a breeze.
- The ability to knock down a container and rebuild it from scratch is fantastic.
- It would be nice if Docker had its own frontend GUI.
- The CLI is very difficult unless you have decent amount of Linux experience.
- Stacks are still a mystery to me.
July 13, 2019
Linux everywhere!
Docker is used by our company to build our server deployment files and to run tests. This allows us to have confidence that our deployments will work correctly in our pull request tests. Developers can also be confident that the build will run the same every time no matter where the code is being run.
- The OSX management tool is simple to use.
- It is nice to be able to use custom repositories.
- The service runs mostly in the background now, and I don't have to tinker with it .
- Sometimes issues arise running images, that are only cleared by removing the cache and restarting the OSX app.
- It is easy to build up a lot of containers that aren't being used, and you have to manually clear them up.
- It would be nice to have a better graphical interface to see what is going on internally.
May 10, 2019
Docker for all your container needs!
Instead of using VMs for our testing environments in our automated pipelines, we use Docker containers to simplify and increase the efficiency of our testing. We needed a testing environment that worked both for Windows and Linux, so Docker was the best choice for our scenario. It is being used on a team-by-team basis.
- Containers - Docker is the go-to when using Containers, which are super useful if you need an environment that works both for Windows and Linux
- Efficiency - Docker is very lightweight and doesn't demand too much from your CPU or server
- CI/CD - Docker is excellent for plumbing into your build pipeline. It integrates nicely, is reliable, and has an easy set up.
- Security - Since there's no true operating system, you're pretty limited when it comes to security in Docker. But that's with all containers.
- Not totally isolated - Docker containers all use the same kernel, so if you've got multiple Docker containers up on one server, you could run into some issues.
- Network connectivity - There's a fine line between limiting network access but also having proper communication where needed, since you don't have a full OS with Docker
November 09, 2018
Docker can decouple VM provisioning and deploy.
We use Docker as part of a rapid deployment project that allows a service to be easily deployed directly onto VMs automatically during staging and production. It makes the management of the VM a parallel task to the deploy process. Traditionally the provision of a VM would be intertwined with the deploy process and containerization allows for these things to be decoupled.
- Containerization - allowing multiple micro-services to function together without in-depth orchestration at the VM level.
- Rapid deployment - a developer with appropriate access can simply push to the correct remote and the deploy happens automatically from there
- Decouples provisioning from VM administration - allows containers to be deployed (more) regardless of VM set up.
- Containers are often opaque - if a container doesn't work out of the box, it's messy to fix.
- Logging is complexified by the multiple containers and logs are often not piped to places you expect them to be.
- Networking is complexified due to internal port mapping between containers, etc.
Docker is being used across our organization for product development and deployment. We switched to docker in order to replace a custom build and deploy the solution. We have used it as part of our build and deploy system to make the process more flexible and decentralized. It has made it much easier to build out new data centers and is part of our internationalization strategy.
- Docker provides encapsulation of our deployed software. This allows us to consistently deploy each of our services and webs in a customizable manner.
- Docker makes it easy to build and release software in both development and production environments
- Docker allows us to build common baseline environments for consistency across apps while adding app-specific customizations.
- We have had problems using Docker for local development. There are issues with how it works with our asset build system.
March 23, 2018
Hive Mind Your Frontend
We are using Swarm for our analytics gathering service. Using swarm allows for quick workload scaling and using less hardware than was needed before.
- Creating complex containers using docker files which automate a lot of DevOps manual labor
- Having some preconfigured containers to do fast tests
- The swarm takes away a lot of the work you would need to do for high availability
- Kitematic UI is still very limited in functionality
- Containers on Windows are somewhat hit and miss, Linux is strongly recommended
- Swarm interface is mostly command line
- Some network limitations (like remote client IP passthrough)
March 03, 2018
Docker: Streamlined DevOps with a little overhead
Docker is used across our whole engineering organization. It is used to simplify packaging and deployment of the apps and services we develop. Using docker allows us to match our development environment more closely to production and run polyglot applications without worrying about cross-cutting software dependencies and server configuration.
- Simple interface for defining and building an application runtime environment. This makes applications easy to inspect because aspects like exposed ports and environment variables can be defined declaratively and consistently.
- Local environment parity with production. Docker manages dependency installation and allows you to easily run apps locally in the same environment as they run in production, giving you confidence that your app will work as expected when deployed and making configuration-related bugs easier to reproduce.
- Makes applications easy to publish and distribute. Docker's image registry makes it extremely easy to publish your applications and distribute them securely. This makes deployment much simpler and provides version control for your application artifacts, making rollbacks very easy.
- Docker has a bit of a learning curve, and it takes some time to become familiar with the tooling and syntax. Transitioning an existing architecture to docker can represent a significant investment.
- Docker attempts to provide some level of cross-host container orchestration via swarm, but it falls short of third-party solutions like Kubernetes.
- We occasionally run into stability issues when the docker daemon is subjected to high load (many applications starting/stopping frequently). In these cases, docker hangs and we have to restart or replace the node.
January 30, 2018
Quick Docker Review
Docker is used across our whole engineering organization in order to have a consistent dev environment for local testing. We also use Docker for our microservices on Rancher. Docker is extremely useful as we can easily spin up any sort of environment we want and create/test new features. The use of Docker also helps prevent those "it work on my computer" type of issues.
- Flexibility
- Ease of Use
- Very powerful
- Can be seen as a black box
- Hard to debug if unfamiliar with it
- Semi-steep learning curve
August 16, 2017
Docker FTW!
We use Docker to containerize our applications, we get many benefits from this such as:
- consistent, realizable deployment environments across dev, QA, prod - the same image used in dev is the exact same image deployed to production
- better utilization of server resources
- cross cloud compatibility
- the ease of scaling applications
- Docker makes deployments easier across environments.
- Docker allows to better utilization of server resources by easily allowing multiple applications (images) to run on the same server.
- Docker makes it easy to scale our applications out.
- Docker is somewhat new and new functionality comes with each release, sometimes it can be hard to stay on top of all the new features.
- It would be nice if a full GUI based container management system came with Docker.
August 15, 2017
Docker for QA: dockerized Selenium Grid
Docker is used for by both the dev team and the QA team on my project. For the dev team it's really useful as they had a lot of issues prior to using Docker with the different setups the devs had: Win/Linux/Mac. After switching to Docker these issues disappeared.
For me as an automation QA lead, it's mainly used for our Selenium Grid. Our grid is running on AWS, and I configured it via Docker. I use docker-compose to start it up and to scale how many browsers should be started. Using only Docker was already a huge help, as we didn't really have to worry about the configurations and it was easy to use the same setup for more instances, but combined with the scaling option of docker-compose it proved to be a really convenient.
For me as an automation QA lead, it's mainly used for our Selenium Grid. Our grid is running on AWS, and I configured it via Docker. I use docker-compose to start it up and to scale how many browsers should be started. Using only Docker was already a huge help, as we didn't really have to worry about the configurations and it was easy to use the same setup for more instances, but combined with the scaling option of docker-compose it proved to be a really convenient.
- Develop on multiple platforms. The same Docker image can be used on Linux/Mac/Windows.
- Ease of configuration. It's very easy to create a base image for your project. There are a lot of already existing images you can use to start with.
- Scalability. If you need more than just one instance of the same image, it's just a command to spin up more.
- Finding the perfect configuration: it's very easy to find some basic configurations, but fine-tuning it can be challenging.
- Understanding the concept can be difficult at first. Most of the question I get from colleagues are around: what's happening inside the docker, how we can see the logs what happens inside etc. One you have the concepts, you can easily do these, but this can be a rough beginning.
- Sometimes difficult to set it up. I'm mainly hearing about this from colleagues using Windows.
August 04, 2017
Docker, Pros, Cons, Use Cases
A large global financial services provider based in London, faced increasing regulatory pressure and market demands—led by industry disruptors offering modern, digital services. Looking to increase innovation and productivity, Barclays set out to build an Application Platform-as-a-Service as part of its cloud program. It used Red Hat OpenShift Container Platform which incorporates Docker, along with other Red Hat solutions to update its IT infrastructure and adopt an agile, DevOps approach to application development, giving its developers on-demand, self-service capabilities. As a result, the bank improved its efficiency and agility to innovate faster and stay competitive.
- Docker brings in an API for container management, an image format and a possibility to use a remote registry for sharing containers. This scheme benefits both developers and system administrators.
- Docker allows for portability across machines. The application and all its dependencies can be bundled into a single container that is independent of the host version of Linux kernel, platform distribution, or deployment model. This container can be transfered to another machine that runs Docker and executed there without compatibility issues.
- Docker has a lightweight footprint and minimal overhead. Docker images are typically very small, which facilitates rapid delivery and reduces the time to deploy new application containers.
- Docker allows for sharing. You can use a remote repository to share your container with others.
- Docker provides great version control and component reuse. You can track successive versions of a container, inspect differences, or roll-back to previous versions. Containers reuse components from the preceding layers, which makes them noticeably lightweight.
- Docker has got into the bad habit of wrapping open source Linux technologies and promoting them in a way that makes it feel like Docker invented it. They did it to LXC and they are doing it to aufs and overlayfs.
- Docker is not very developer friendly.
- Docker containers are currently for software, not for data.
- New Docker versions cause breakage. You need all kinds of subtle regressions between Docker versions. It’s constantly breaking unpredictable stuff in unexpected ways.
- Docker does not have a command to clean older images, lifecycle management.
- Lack of kernel support.
June 26, 2017
Testing with Docker
Docker is being used by us to create and throw away spaces as needed for testing. Instead of managing a huge hardware lab we are able to "spin up" configurations as needed. If we need a new configuration to test against we just build a new container. It makes life more simple.
- Docker is fast.
- Docker is well documented.
- Docker has public container registries.
- Docker storage is still hard.
- Docker has poor monitoring.
- Docker is platform-dependent.
April 19, 2017
Great open source software for reliable automation.
Recently at Monsanto, there is a big push towards a DevOps model and micro-services. As our first step towards moving to the cloud, we started using docker to spin up new databases for various micro-services. When moving towards micro-services, we need a simple and consistent way to spin up database instances that do not affect each other. We needed consistency because we want the instances to be same across different environments.
- Simple and reliable way to replicate instances.
- Not needing to worry about internal workings of the instance as Docker takes care of managing the instance.
- Very well documented API with large community support.
- Verifiable Docker files, that allow us to look at what exists within a Docker file.
- Managing backups of Docker instances does not scale well as the size of instance grows. The entire Docker instance needs to be stopped for the backups to happen and it's not always scalable.
- While there are a lot of useful methods on CLI. The API for CLI is slow to evolve, leaving much to be desired. For example executing commands on the Docker instances, maintaining instances requires hacks using the CLI.
- Writing a Docker file and debugging it is not always intuitive. Requires some trial and error to get it right.
April 05, 2017
Docker - LEGOs for System Admins
Docker allows us to provision identical instances across our various systems (testing, staging, production, etc.). Docker has also allowed us to drastically reduce our spin up time for new instances, as all of the components that we commonly use have been converted into Docker Files.
Additionally, because of the great community behind Docker, many of the components that we use (MySQL, Tomcat, etc.) already have Docker files for them, many of which are awesome, and are easily adaptable (if necessary) to best suit the needs of our department.
Additionally, because of the great community behind Docker, many of the components that we use (MySQL, Tomcat, etc.) already have Docker files for them, many of which are awesome, and are easily adaptable (if necessary) to best suit the needs of our department.
- Easy to understand, with excellent documentation and community support.
- Easy to deploy to a variety of platforms.
- Allows for containers to be quickly be built, destroyed, transferred, all while keeping them consistent.
- Docker files can be limiting, because of the core idea of Docker, with only one process per container.
- Debugging DockerFiles can be a nightmare.
- Some configurations for a container cannot be updated post creation.
- There can be some trial-and-error associated with deploying containers and their corresponding Docker files.
April 03, 2017
Docker is for microservices and app delivery
We are using Docker today to spread multiple Tomcat instances across a single machine. Docker is currently being used by our devops team but we're a small company so that's pretty much the entire infrastructure team as well. Docker helps us keep our configs simple, easy to use, and reproducible in a really efficient manner.
- Docker makes it very easy to reproduce a service build and configuration. This is huge for rolling out quickly and efficiently.
- Docker can orchestrate your containers to auto scale up and down with Docker Compose. This is very useful on cloud providers where you pay for instance to keep prices down.
- Docker's intra-container networking works well for the most part but it does leave something to be desired when attempting to weave a complex deployment of microservices across multiple bare metal machines and networks. It would be nice to introduce some sort of modeling tool into container networking.
- A really neat feature for Docker could be to have an option to analyze container utilization and alert or notify on suggestions to improve efficiency.
March 24, 2017
Docker rocks!
We are just beginning to use Docker for some specialized microservices within our existing server infrastructure. Specifically, we use it to run a Selenium Grid for automated web-based testing. We are considering broader adoption of Docker within areas such as Java application deployment, local development environments, and continuous integration. Docker primarily helps us maintain environmental consistency (having the same environment from local development to deployment in the cloud).
- abstracting the virtualization aspects so that I don't need to know every detail (even to the point of not needing to know if Docker is using a VM behind the scenes or not)
- providing a simple yet powerful configuration scheme
- huge selection of base containers and easy way to derive from them
- automated builds through Docker Hub
- multiple configuration file versions can be a little confusing
- experienced some downtime with Docker Hub, though it was cleared up quickly
- not really a con of Docker, but it takes some time to learn the concepts of containers and adapt to that way of thinking. Perhaps it would be helpful to have a "Docker for Old School Sys Admins" guide that helps explain some of the differences in concepts and execution when working with containers.
March 07, 2017
Improves Environmental Consistency and Runtime Security
Docker is transforming our confidence in build and release as well as developer onboarding. Docker containerization finally is fulfilling the promise that Chef never did, giving us environmental consistency across developers, build, various environments and production. We've been eliminating deployment time errors by encapsulating the entire operating system, language core components, security patches, etc., into the application build time. This has reduced the complexity of getting developers up and running. No longer do developers and operations have to understand the full workings of the dependencies within an application in order to run and deploy it--instead, we only need to know how to get Docker running and deployed to get our applications up and running. This allows us to have truly ephemeral environments and dependency management and eases autoscaling.
- Environment consistency via full application and operating system encapsulation
- Securing software runtime by ensuring that the whole environment is easily and quickly discarded and re-run from a known good state--as well as putting all dependencies of the operating system and patches into the built artifact
- Easing developer setup time (up and running immediately without installing various software dependencies and configuring ports/etc.)
- The ecosystem has many minimal base images for software but this could use more focus on secure base images
- Many useful Docker commands are not built in as shortcuts to the CLI, but instead need to be managed as other aliases (e.g. `docker rm $(docker ps -a)` to remove all running and stopped containers)
- It's not always easy for people to optimize the caching layers of docker images--an auditing tool that suggests the order of Dockerfile commands for cache optimization would be handy
February 27, 2017
Docker killed the sysadmin, but it did not kill the developer
Docker is being used primarily to host a MySQL database that runs a production website. It has been very stable and easy to work with, and we like the security that containerization affords.
- Security by isolation.
- Ease of deployment.
- Flexible configuration.
- Scalability.
- Resource management.
- Administration simplicity.
March 18, 2016
Docker in play
Its simple and easy to build and run containers on bare metal VMs without much sys admin experience.
- Developers are able to set up workstation in their local in couple of secs.
- docker image pull is taking more time.
- Containers are crashing some times due to teh file system or daemon issue.
March 11, 2016
Docker...a huge win!
We are using Docker to deploy multiple services for our company.
Docker allows us to deploy more stable apps, since containers provide an identical application-environment across multiple deployment-environments.
Docker also allows us to differentiate between server/compute infrastructure and application infrastructure.
Ops manages the cluster of servers, while application developers simply run containers on the cluster.
Docker allows us to deploy more stable apps, since containers provide an identical application-environment across multiple deployment-environments.
Docker also allows us to differentiate between server/compute infrastructure and application infrastructure.
Ops manages the cluster of servers, while application developers simply run containers on the cluster.
- Application Runtime Provisioning: Instead of requiring a devops engineer to craft a lengthy provisioning configuration for an application, Devs can easily create a Dockerfile that builds the exact runtime needed for their applications
- Polygot environments: Now that services are are individually provisioned for their task (as opposed to servers provisioned for their task) polyglot services are much more simple. Using the best-tool-for-the-job is simple
- Scaling is easy: Need to scale a service from 5 to 15 nodes? Simply run 10 more containers across the server cluster. Startup is near instant for containers.
- Application Architecture has Improved: Before Docker, our team was nowhere close to 12-factor applications. Docker has allowed us to still manage our own infrastructure, yet we're now building highly-scalable 12-factor apps.
- Service registration and discovery could easily be implemented into Docker/Swarm and would make new-infrastructure startup much simpler.